home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941221-19950208
/
000003_news@columbia.edu_Wed Dec 21 22:32:02 1994.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA24006
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 21 Dec 1994 17:32:05 -0500
Received: by apakabar.cc.columbia.edu id AA10500
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 21 Dec 1994 17:32:04 -0500
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: a friend having a problem
Date: 21 Dec 1994 22:32:02 GMT
Organization: Columbia University
Lines: 31
Message-Id: <3daad2$a80@apakabar.cc.columbia.edu>
References: <pX3-kuqcZBFF075yn@primenet.com> <1994Dec21.102006.35857@cc.usu.edu>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <1994Dec21.102006.35857@cc.usu.edu>,
Joe Doupnik <jrd@cc.usu.edu> wrote:
>In article <pX3-kuqcZBFF075yn@primenet.com>,
>jbishop@primenet.com (Jeff Bishop) writes:
>>
>> Description: Computer locks up solid if "set receive packet-length 2000"
>> is a parameter when calling Kermit from a {Commo} macro.
>> ...
>Those omitted details show that program COMMO is attached to the
>serial port hardware. That will be fatal if Kermit also uses the same
>hardware. Thus I recommend you try without COMMO.
>
On the other hand, MS-DOS Kermit 3.14 is specifically designed to be used
as an external protocol by other software, so if Commo leaves the port
alone while Kermit is using it, hopefully there will be no interference.
Two other possibilities spring to mind. When you add this command, you
are doing two things: making the command line longer, and causing Kermit
to dynamically allocate memory for packet buffers.
If the command line is longer than DOS's buffer for command lines (if I
recall correctly), terrible things can happen. It is better to use a
shorter command line which points Kermit at a file to execute additional
commands from.
If that's not the explanation, then look at your memory management setup
very carefully -- maybe more than one process is contending for the same
memory, or QEMM is misconfigured, or Commo is not respecting Kermit's
"space", or some other application, driver, or TSR is misbehaving.
- Frank